Search Results

The Location Referencing Message Specification (LRMS) standardizes location referencing for ITS applications that require the communication of spatial data references between databases. ITS databases may reside in central sites, vehicles, or devices on or off roads or other transportation links. The LRMS is applicable to both homogeneous (same database) and mixed database environments that may be implemented on wireless or landline networks. While developed for ITS applications, the LRMS may be used for non-ITS applications as well within the field of geographic information processing.

This SAE Standard describes standardized medium-independent messages needed by information service providers for Advanced Traveler Information Systems (ATIS). The messages contained herein address all stages of travel (pre-trip and en-route), all types of travelers (drivers, passengers), all categories of information, and all platforms for delivery of information (in-vehicle, portable devices, kiosks, etc.).

This SAE Standard describes standardized medium-independent messages needed by information service providers for Advanced Traveler Information Systems (ATIS). The messages contained herein address all stages of travel (informational, pre-trip and en route), all types of travelers (drivers, passengers, personal devices, computers, other servers), all categories of information, and all platforms for delivery of information (in-vehicle, portable devices, kiosks, etc.).

This SAE Standard describes standardized medium-independent messages needed by information service providers for Advanced Traveler Information Systems (ATIS). The messages contained herein address all stages of travel (informational, pre-trip and en route), all types of travelers (drivers, passengers, personal devices, computers, other servers), all categories of information, and all platforms for delivery of information (in-vehicle, portable devices, kiosks, etc.).

This SAE Standard defines methods and messages to efficiently translate sequences of text and other types of data into and out of indexed values and look-up tables for effective transmission. This document defines: a Methods and Data Elements for handling indexes and strings in ATIS applications and message sets b Message Sets to support the delivery and translations of tables used in such strings c Tables of Nationally standardized strings for use in ATIS message descriptions And examples of each in illustrative portions. While developed for ATIS use, the methods defined in this document are useful for any textual strings in any Telematics applications found both in Intelligent Vehicles and elsewhere.

This SAE Standard defines methods and messages to efficiently translate sequences of text and other types of data into and out of indexed values and look-up tables for effective transmission. This document defines: a Methods and Data Elements for handling indexes and strings in ATIS applications and message sets b Message Sets to support the delivery and translations of tables used in such strings c Tables of Nationally standardized strings for use in ATIS message descriptions And examples of each in illustrative portions. While developed for ATIS use, the methods defined in this document are useful for any textual strings in any Telematics applications found both in Intelligent Vehicles and elsewhere.

This report specifies the minimum requirements for the Road Geometry and Attributes (RGA) data set (DS) to support road geometry related motor vehicle safety applications. Contained in this report are a concept of operations, requirements, and design, developed using a detailed systems engineering process. Utilizing the requirements, the RGA DS is defined, which includes the DS Abstract Syntax Notation One (ASN.1) format, data frames, and data element definitions. The requirements are intended to enable the exchange of the messages and their DS information to provide the desired interoperability and data integrity to support the applications considered within this report, as well as other applications which may be able to utilize the DS information. System requirements beyond this are outside the scope of this report.

SAE J2945/A and this Abstract Syntax Notation (ASN.1) file precisely define the structure of the data used to implement applications conformant to the Recommended Practice. Using the ASN.1 specification, a compiler tool can be used to produce encodings using encoding rules identified in J2945/A. Both this ASN.1 file and the SAE J2735 ASN.1 files are necessary to collectively implement the data structures described in the J2945/A. The combined library can be used by any receiving application (along with the additional logic of the application). SAE J2945/A also provides recommendations for the interface for sending and receiving Road Geometry and Attributes (RGA) messages. It provides the information necessary to build interoperable applications that rely on RGA messages.

This SAE Standard provides a table of textual messages meeting the requirements for expressing the names of street and roads and some basic building blocks for phrases commonly used in the ITS industry. The tables provided herein are taken from SAE J2369, and follow the rules of SAE J2540 and therefore allow a local representation in various different languages, media expressions, etc. to allow true international use of these phrases. The phrases are predominantly intended to provide a means to express street names including pre and post fixes ( North Oak Street is an example name with a prefix “North” and main portion “Oak” and a suffix “Street”). Other phrases exist for other specific specialty areas of ITS, and all such phrases follow a set of encoding and decoding rules outlined in SAE J2540 to ensure that the use of these phrases in messages remain interoperable between disparate types of user equipment.

This standard specifies the system requirements for an on-board vehicle-to-vehicle (V2V) safety communications system for light vehicles1, including standards profiles, functional requirements, and performance requirements. The system is capable of transmitting and receiving the SAE J2735-defined basic safety message (BSM) [1] over a dedicated short range communications (DSRC) wireless communications link as defined in the Institute of Electrical and Electronics Engineers (IEEE) 1609 suite and IEEE 802.11 standards [2] to [6].

This SAE Standard specifies the system requirements for vehicle-to-vehicle (V2V) safety system for FHWA vehicle classes 1 (motorcycles and 4 through 13 (non-light-duty), including functional requirements and performance requirements. The system can transmit and receive the SAE J2735-defined BSM over a wireless communications interface; the communications interface itself is outside the scope of this document. This document provides the specifications necessary to build interoperable systems that support V2V safety applications for non-lightweight vehicles, as well as motorcycles which rely on the exchange of BSMs. The document covers vehicle classes not addressed in SAE J2945/1 and SAE J3161/1.

This document specifies a set of rules for the creation and management of the V2X ASN.1 Module Collection. These rules apply to the development of any message, data element, data frame, or any ASN.1 Entity that is part of the V2X ASN.1 Module Collection, regardless of the SAE technical report in which it appears. The intended audience for these rules includes every technical committee (TC) under the SAE V2X Communications Steering Committee.

This SAE standard specifies a message set, and its data frames and data elements, for use by applications that use vehicle-to-everything (V2X) communications systems. While the data dictionary was originally designed for use over DSRC, this document is intended to be independent of the underlying communications protocols used to exchange data between participants in V2X applications.

This SAE standard specifies a message set, and its data frames and data elements, for use by applications that use vehicle-to-everything (V2X) communications systems. While the data dictionary was originally designed for use over DSRC, this document is intended to be independent of the underlying communications protocols used to exchange data between participants in V2X applications.

This SAE Standard specifies a message set, and its data frames and data elements, for use by applications that use vehicle-to-everything (V2X) communications systems.

This SAE Standard specifies a message set, and its data frames and data elements, for use by applications that use vehicle-to-everything (V2X) communications systems.

This Abstract Syntax Notation (ASN.1) File is the precise source code used for SAE International Standard J2735. As part of an international treaty, all US ITS standards are expressed in "ASN.1 syntax". ASN.1 Syntax is used to define the messages or "ASN specifications". Using the ASN.1 specification, a compiler tool produces the ASN library which will then be used to produce encodings (The J2735 message set uses UPER encoding). The library is a set of many separate files that collectively implement the encoding and decoding of the standard. The library is then used by any application (along with the additional logic of that application) to manage the messages. The chosen ASN tool is used to produce a new copy of the library when changes are made, and it is then linked to the final application being developed. The ASN library manages many of the details associated with ASN syntax, allowing for subtle manipulation to make the best advantage of the encoding style.

This Abstract Syntax Notation (ASN.1) File is the precise source code used for SAE International Standard J2735. As part of an international treaty, all US ITS standards are expressed in "ASN.1 syntax". ASN.1 Syntax is used to define the messages or "ASN specifications". Using the ASN.1 specification, a compiler tool produces the ASN library which will then be used to produce encodings (The J2735 message set uses UPER encoding). The library is a set of many separate files that collectively implement the encoding and decoding of the standard. The library is then used by any application (along with the additional logic of that application) to manage the messages. The chosen ASN tool is used to produce a new copy of the library when changes are made, and it is then linked to the final application being developed. The ASN library manages many of the details associated with ASN syntax, allowing for subtle manipulation to make the best advantage of the encoding style.

This Abstract Syntax Notation (ASN.1) File is the precise source code used for SAE International Standard J2735. As part of an international treaty, all US ITS standards are expressed in "ASN.1 syntax". ASN.1 Syntax is used to define the messages or "ASN specifications". Using the ASN.1 specification, a compiler tool produces the ASN library which will then be used to produce encodings (The J2735 message set uses UPER encoding). The library is a set of many separate files that collectively implement the encoding and decoding of the standard. The library is then used by any application (along with the additional logic of that application) to manage the messages. The chosen ASN tool is used to produce a new copy of the library when changes are made, and it is then linked to the final application being developed. The ASN library manages many of the details associated with ASN syntax, allowing for subtle manipulation to make the best advantage of the encoding style.

This Abstract Syntax Notation (ASN.1) File is the precise source code used for SAE International Standard J2735. As part of an international treaty, all US ITS standards are expressed in "ASN.1 syntax". ASN.1 Syntax is used to define the messages or "ASN specifications". Using the ASN.1 specification, a compiler tool produces the ASN library which will then be used to produce encodings (The J2735 message set uses UPER encoding). The library is a set of many separate files that collectively implement the encoding and decoding of the standard. The library is then used by any application (along with the additional logic of that application) to manage the messages. The chosen ASN tool is used to produce a new copy of the library when changes are made, and it is then linked to the final application being developed. The ASN library manages many of the details associated with ASN syntax, allowing for subtle manipulation to make the best advantage of the encoding style.